Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1479

reference: 171-tree-1
name: 1479
tree-preservation-order: undefined
171-tpo-1
uprn
address-text
point: POINT (-0.940237 50.862948)
geometry: MULTIPOLYGON (((-0.940152 50.862938,-0.940156 50.862955,-0.940167 50.862970,-0.940186 50.862982,-0.940210 50.862990,-0.940236 50.862993,-0.940262 50.862991,-0.940286 50.862983,-0.940305 50.862972,-0.940318 50.862957,-0.940322 50.862940,-0.940319 50.862923,-0.940307 50.862908,-0.940288 50.862896,-0.940265 50.862888,-0.940238 50.862885,-0.940212 50.862888,-0.940188 50.862895,-0.940169 50.862907,-0.940156 50.862922,-0.940152 50.862938)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL